I Disconnected Power to My Board and Now I Can No Longer Connect via FDL, csoc download, the Keil Debugger, or TMJS. What Do I Do Now?

Cycling power on your E5 or A7 target board during debugging can sometimes confuse the FastChip download/debug mechanism. This article describes a reliable means to disconnect and re-apply power to your target board.

In summary, launch the Triscend MultiJTAG Server (TMJS) software from a command window or DOS box. Before disconnecting power, issue a terminate command from TMJS. After re-applying power, issue a connect command from TMJS.

Separately Start TMJS Server

Before running FastChip Device Link (FDL), the csoc download or csoc debug command, or your source-level debugger, start the Triscend MultiJTAG Server (TMJS) from a command prompt or DOS box. Enter the TMJS command appropriate for your specific environment. The following example assumes that you are using the E5 Evaluation Board, the E5 Development Platform, or the Macraigor Wiggler cable for E5 applications. The assumed communication port is 5005.

tmjs –a e5wig 5005

This command invokes the Triscend MultiJTAG Server and connects to the target board. Be sure that the TMJS status displays “Server is running.” The TMJS server is persistent until shut down.

TRISCEND MULTIJTAG SERVER COMMANDS

help : display Triscend MultiJTAG Server help.

exit/quit : disconnect target, terminate JTAG server & exit.

status : show JTAG server connection status & settings.

connect : launch JTAG server & connect to target.

terminate : disconnect target & terminate JTAG server.

clear : clear target name & host port settings.

Launching JTAG server & connect to target 'TE5_Jtag_Wiggler' on port 5005

Server is running.

Opening TCP/IP channel to JTAG server on port 5005

TCP/IP channel is open.

Status : Server is running.

Settings: TE5_Jtag_Wiggler, port 5005

tmjs<

Invoke TMJS with additional debugging information using the –v option. Status messages from the low-level “spiderd” JTAG server appear in a separate window. The additional window may overlap the TMJS window. Simply drag the “spiderd” window to another location on your screen to reveal the TMJS window.

Example: tmjs –a –v e5wig 5005.

Download/Debug Target

After launching TMJS, you can invoke any of the applications that communicate with the target board, such as FDL or your source-level debugger. For example, launch FastChip Device Link and download to the target board. If your target board is powered and TMJS is running, your download should be successful.

Disconnecting Power

From the TMJS console window, issue a terminate command. TMJS then issues a warning instructing you to shut down all other clients such as FDL, csoc download, or your source-level debugger before finally terminating TMJS. Ignore this warning and press the <Enter> key.

tmjs< terminate

*************************************************************

***************** WARNING *****************

*************************************************************

There is 1 other client still connected to the JTAG server.

Other clients might be:

FDL, FastChip, CSoC Debug/Download, or KEIL-uVision2.

First shutdown all other clients before terminating JTAG server.

Press 'ENTER' to continue terminating the JTAG server...

Terminating JTAG server...

Server is not running.

Status : Server is not running.

Settings: TE5_Jtag_Wiggler, port 5005

If you are running FDL, you will see the following error message. Ignore this message for the moment.

IGNORE this FDL error message for the moment.

"No communication with target.
For more details, please see the
Command Output window or click
the Help button."

Disconnect power from your target board.

Re-applying Power

Re-apply power to the target board.

From the TMJS window, reconnect to the target hardware using the connect command. Verify that TMJS reports that the “Server is running.”

tmjs< connect

Launching JTAG server & connect to target 'TE5_Jtag_Wiggler' on port 5005

Server is running.

Opening TCP/IP channel to JTAG server on port 5005

TCP/IP channel is open.

Status : Server is running.

Settings: TE5_Jtag_Wiggler, port 5005

If you are using FDL, now click Retry to re-establish communication with the target board.

Click "Retry" to re-establish communication with the target board.

Verify that FDL successfully re-established communication with the target board. In the Command Output window, verify that FDL reports “Connected to Target” and “CSoC running.”

Verify that FDL established communication with the target board.

FDL should report "Connected to target" and "CSoC running."

You should now be able to resume download and debugging to your CSoC target hardware.

FastChip Version: 2.3.0

This solution may or may not apply to other versions of the FastChip development system.